Attribution issue

• issueId: issue_mo8yyyaa_5bvzp9
• category: tool
• canonicalTitle: MCP工具命名/描述不足以引导正确调用
• representativeRun: atomic-js-cloudbase-list-functions/2026-04-21T18-40-28-ad7ixi

Automation summary

• root_cause: The MCP tool queryFunctions and manageFunctions had action descriptions that only gave examples (e.g., "只读操作类型，例如 listFunctions、getFunctionDetail、listFunctionLogs") without explicitly mapping actions to their purposes. This made it unclear to the model that to list functions, it should call queryFunctions with action="listFunctions". The model returned a 400 error without making any tool call because it couldn't determine the correct way to invoke the tool.
• changes: Updated queryFunctions and manageFunctions tool descriptions to explicitly state how to use them, following the pattern used by auth and envQuery tools:
• queryFunctions: Added explicit description "要获取所有云函数列表，请使用 action="listFunctions"" and updated action description to use action=purpose format: "listFunctions=获取云函数列表，getFunctionDetail=获取函数详情..."
• manageFunctions: Updated action description to use action=purpose format: "createFunction=创建云函数，updateFunctionCode=更新函数代码..."
• queryAgents and manageAgents: Applied the same pattern for consistency
• validation: All tests passed (325 passed, 17 skipped), including the three regression tests (build-skills-repo.test.js, build-com

Changed files

• doc/prompts/auth-web.mdx
• mcp/src/tools/agents.ts
• mcp/src/tools/functions.ts